The following lists some examples of session criteria for the EDI Session form (on page 1):
Example 1: An outbound ACTIVITY EDI session for gate activity for a line operator
For example, to include only units with a line operator of ABC and only deliver and receive container gate activity in an extract, you can define the following session criteria for an outbound ACTIVITY EDI session:
Example 2: An outbound ACTIVITY EDI session for vessel activity for a line operator
For example, to include only vessel activity (container loads or discharges) in an extract for units that have any of the following:
ABC as the line operator
ABC as the equipment operator
ABC as the vessel operator, to include alliance partners on an inbound or outbound ABC vessel
You can define the following session criteria for an outbound ACTIVITY EDI session:
Example 3: An outbound STOWPLAN EDI session
For example, to include only units with a line operator of ABC or ANL in an extract, instead of all of the units on a vessel, you can define the following session criteria for an outbound STOWPLAN EDI session:
Example 4: An outbound ACKNOWLEDGEMENT EDI session
For example, to send outbound APERAK EDI messages back to the associated EDI trading partner when N4 processes inbound BOOKING EDI transactions with ERRORS, you can define the following session criteria for an outbound ACKNOWLEDGEMENT (on page 1) EDI session using the APERAK EDI message type:
Example 5: An outbound INVENTORY EDI session
For example, to include only unit facility data located in the MAIN facility, you can define the following session criteria for an outbound INVENTORY (on page 1) EDI session:
